home *** CD-ROM | disk | FTP | other *** search
-
- >> Unlike PC/TCP, Distinct is DLL based, and doesn't require a giant chunk of
- >> your precious 640k of DOS memory. In fact, when it is not active it requires
- >> only about 4k of memory. PC/TCP (which I also have on some machines I
- >> support), being a TSR base stack, uses between 50k and 90k of DOS memory ALL
- >> THE TIME!
- >>
- Ahem; we have many memory footprints depending on hom you load our
- kernel but 50K isn't even close to one of them. We have a ~25K profile
- with data in low memory and code in EMS, a ~70K profile with code and
- data in low memory and a (ha ha - doncha love marketing :-) ) 0K profile
- with both code and data loaded into UMB. All of these profiles grow
- depending on how many extra packet buffers you use past the default of
- 5. A 90K profile is a distinct possibility with 15 packet buffers;
- I have never seen a 50K profile....
-
- As to those "look ma, only 6K of memory" claims, it is most definately true
- that a DLL stack can be loaded and unloaded dynamically; thus leaving
- a small footprint when its not around. But...have a look with Heapwalker
- at how much low memory a DLL stack takes up when loaded.
-
- Its interesting that a decent protocol stack must be present at interrupt
- time; right? So what kind of memory is needed by Windows in order to
- keep code present at interrupt time. Locked & Fixed; right? I leave it
- as an exercise to the reader as to where locked and fixed memory comes
- from. TANSTAAFL.
-
- Larry Backman
- FTP Software
-
-